remove HiveConf and Configuration from thread-local after conection to h... #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
...iveserver is closed. I was done to clean sharkserver memory after all clients connections are closed. Without this fix I see about 200 HiveConf and about 200 hadoop Configuration instances in sharkserver memory even if all connections are closed and server is idle for a long time. HiveConf and Confugiration are quite large instances - about 100-150KB each. Totally they use about 40-60 MB of memory


before:
after: